Choose which notification rows your user receives. A checked row means your user is subscribed. It does not prove an email arrived.
Who can use this. Settings is available to a super admin or an admin. A subscription is stored for the signed-in user. Some messages still go to the customer, or to an internal admin, even when you clear a row.
Before you start. Open the correct business first. Notification names are loaded from the server. The dashboard prints the name with underscores replaced by spaces, plus the description stored for that row.
Steps
- Open Settings, then the Notifications tab.
- Wait for the list. If it fails, the screen reports that it failed to fetch data. Open the tab again after you confirm the business.
- Read each label. You may see payment link paid, wallet closed, payment voided, invoice created, payment link created, recurring payment created, recurring payment approved, recurring payment failed, virtual terminal payment, verify email, and wallet auto closed, depending on which rows exist for your account.
- Turn a row on. The toast says Notification added successfully.
- Turn a row off. The toast says Notification removed successfully.
| What you see | Meaning | What happens next |
|---|---|---|
| payment link paid | A payment link was paid in full. | Can email the customer and subscribed merchants. |
| payment link created | A link was created or resent. | Emails the customer. A separate setting can disable the customer copy. |
| invoice created | An invoice was sent. | Emails the customer. |
| virtual terminal payment | A Virtual Terminal sale was approved, or a receipt was sent from the transaction. | Emails the selected recipient. |
| payment voided | A voided payment receipt was requested. | Emails the merchant and the customer when that send action is used. |
| recurring payment approved | A scheduled charge was approved. | Emails the customer. Subscribed merchants use the same preference name. |
| recurring payment failed | A scheduled charge was declined. | Emails the customer and subscribed merchants. |
| Wallet Closed | A wallet was closed. | Emails the business owner. This is separate from the permission row named wallet closed. |
| Wallet Auto Closed | The daily close job closed wallets. | Goes to internal admins with the admin wallet notification permission, not to every merchant. |
| verify email | The account email must be verified. | Goes to the user who must verify. Turning off other rows does not stop this. |
| new merchant registered | A registration reached the admin notification. | Internal. It is not a customer receipt. |
After you save or submit. The checkbox changes subscription membership only. Mail is queued by the event. The dashboard does not show a delivered or read status for that email.
Example. Example only: Sam wants a receipt when a payment link is paid. Sam opens Settings, Notifications, and turns on payment link paid. Later a fictional 18.00 link is paid. Sam should look for the email, and should also open Transaction History, because a missing email does not mean the payment failed.
Troubleshooting
- Not receiving notifications. Confirm the row is on, you are in the right business, and the event really happened. Customer messages are not controlled by every merchant checkbox. Check spam. The screen cannot show whether the mailbox accepted the message.
- wallet closed describes a bank deposit. That description text is stored on the notification row. Closing a wallet does not by itself show the date funds reach the bank.
- Checkout API receipts. The checkout paid email class is not sent by the successful checkout handler in this API. Do not wait for that email as proof of payment. Use Checkout Sessions and Transaction History.
Related
Found this helpful?
( 0 out of 1 found helpful )